Index
Subject
: [lug] Digest (8 messages)
From
: lug-owner@lists.ncsu.[redacted]
Date
: Sun, 16 Apr 2017 22:58:17 -0400
The Lug Digest
Volume 1 : Issue 406 : "text" Format
Messages in this Issue:
201704/1 : Tuesday 4/4 Social Dinner
Quentin Young <qlyoung@ncsu.[redacted]>
201704/2 : Tonight's meeting location
Quentin Young <qlyoung@ncsu.[redacted]>
201704/3 : Tuesday Hack Night
Quentin Young <qlyoung@ncsu.[redacted]>
201704/4 : 2017 SouthEast LinuxFest
"George P. Burdell" <info+lug@southeastlinuxfest.[redacted]>
201704/5 : LUG / ACM Event Tomorrow
Quentin Young <qlyoung@ncsu.[redacted]>
201704/6 : Using sed to straighten quotes.
Jeffery Mewtamer <mewtamer@gmail.[redacted]>
201704/7 : Re: Using sed to straighten quotes.
Quentin Young <qlyoung@ncsu.[redacted]>
201704/8 : Re: Using sed to straighten quotes.
Jim Turner <jdturne8@ncsu.[redacted]>
----------------------------------------------------------------------
Date: Mon, 3 Apr 2017 00:17:27 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Tuesday 4/4 Social Dinner
Message-ID: <dcf1ce58-0cba-9893-c731-6ab5368c0ce3@ncsu.[redacted]>
Hi LUG-
The poll for this week's social meeting is up at:
https://forum.lug.ncsu.edu/t/tuesday-4-4-social-dinner/84
Vote if you're coming and come if you vote!
Be on the lookout for a longer announcement email later this week.
/* (C) POTLUG 2017
* This file is part of POTLUG Weekly Digest.
*
* POTLUG Weekly Digest is free email; you can redistribute it and/or
modify
* it under the terms of the GNU General Public License as published
* by the Free Software Foundation; either version 2, or (at your
* option) any later version.
*
* POTLUG Weekly Digest is distributed in the hope that it will be
useful, but
* WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with POTLUG Weekly Digest; see the file COPYING. If not,
write to the
* Free Software Foundation, Inc., 59 Temple Place - Suite 330,
* Boston, MA 02111-1307, USA.
*/
Quentin
------------------------------
Date: Tue, 4 Apr 2017 18:14:26 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Tonight's meeting location
Message-ID: <CANhSzx3VYf5Cv7shTGEX6fB+hMonuEX48S-R2DwRi4DmSvmt-A@mail.gmail.[redacted]>
Hi LUG-
Sorry for the late notice. Tonight's meeting will be at I <3 NY PIZZA!
Hooray!
I <3 NY PIZZA is on Hillsborough St. near NCSU campus.
Best,
--
Quentin Young
President, LUG @ NC State
[Attachment of type text/html removed.]
------------------------------
Date: Sun, 9 Apr 2017 18:47:23 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Tuesday Hack Night
Message-ID: <f2d8a8d8-9d54-b292-d8a4-3c3f041b2603@ncsu.[redacted]>
Hi LUG,
Last week a grad student was kind enough to donate one of his 1U HP
Proliant DL360 G5 servers to us. This unit has 64gb of DDR2 memory and
two Xeons for a total of 8 physical cores -- in other words, it
out-specs both of our current units. However it didn't come with any
disks, so the LUG has picked up 3x1TB drives to toss in the drive bays.
We'll be doing that and imaging it with our favorite flavor of Linux
this Tuesday night, so anyone who wants to learn about server hardware,
installing Linux, RAID configuration, and other sysadmin-y tasks is
welcomed to join us. Should be a fun meeting.
Time and place as usual, 7:00 P.M. @ EB2 3001.
Oh, and if anyone has M3 screws for mounting the drives into the drive
caddies and feels like sharing, bring 'em! I have some on the way from
Amazon but they're slated for delivery Tuesday, which usually means 7:30
Tuesday night...
Best,
--
Quentin Young
President, LUG @ NC State
------------------------------
Date: Mon, 10 Apr 2017 14:35:55 -0400
From: "George P. Burdell" <info+lug@southeastlinuxfest.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: 2017 SouthEast LinuxFest
Message-ID: <CACsMxkdoHrCAqTq5p7Ygf+hGZrhc_TyG_R5ia5XFSFBFtEGonQ@mail.gmail.[redacted]>
Talk submissions for SELF 2017 closes THIS FRIDAY at 11:59 PM ET. We are
always looking for talk submissions on a very wide variety of topics. As
long as it is geeky and not proprietary ... we're interested! We even had
a talk last year on hardware computers used on WWI Battleships. So if
you're passionate about something -- from programming languages to
development to administration to design to something straight out of
/dev/random -- submit a talk! If you're selected as a speaker at SELF,
we'll treat you to a proper Carolina style BBQ dinner as well as an
unfathomable list of wine, distillates, and microbrews from all over the
South. So what are you waiting for? Submit your talk now:
http://www.southeastlinuxfest.org/?page_id=18
--
George P. Burdell
SouthEast LinuxFest
http://www.southeastlinuxfest.org
@selinuxfest
fb.com/selinuxfest
[Attachment of type text/html removed.]
------------------------------
Date: Wed, 12 Apr 2017 23:14:45 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: LUG / ACM Event Tomorrow
Message-ID: <60888d3b-0e5c-660d-16b4-5761b51093d4@ncsu.[redacted]>
Hi LUG,
As featured in Ken Tate's most recent CSC news, a joint event between
our club and the Association for Computing Machinery will take place
tomorrow from 6 to 7 P.M. in 1231 EB2. A SWE from Red Hat will be
delivering a talk on Docker and LXC (LinuX Containers). Food and drink
will be provided courtesy of ACM + LUG.
I know many of you will be attending TriLUG's meeting tomorrow; those of
you who are not, I look forward to seeing you at the event.
Best,
--
Quentin Young
President, LUG @ NC State
------------------------------
Date: Mon, 17 Apr 2017 00:17:15 +0000
From: Jeffery Mewtamer <mewtamer@gmail.[redacted]>
To: Linux for blind general discussion <blinux-list@redhat.[redacted]>,
lug <lug@lists.ncsu.[redacted]>, raspberry-vi@freelists.[redacted]
Subject: Using sed to straighten quotes.
Message-ID: <CAO2sX336r3GQ6aH4Qh8u5CFyC_m9XazTWos7VVtBCkiPwcGK1g@mail.gmail.[redacted]>
I often convert various document formats to plain text because the
conversion is generally easier than trying to navigate a program that
can read the document in its original format. Problem is, even when
the document is in English or another language that uses the Roman
Alphabet, the converted .txt contains characters my text-mode screen
reader can't read properly(pronouncing the character as "thorn")
Things like left and right double curly quotes and single right curly
quotes are the most common offenders, which also screws up my screen
reader's pronunciation of contractions and possessive, though things
like ellipsis, em-dashes, and accented letters also cause problems.
Most of these problems can be fixed manually, though it means I often
spend as much time correcting the file as I do reading it.
I know how to use sed to do global search and replace on plain text
files, at least where both the string to be found and the string it's
to be replaced with can be typed, but most of the replacements I'd
like to make have search strings containing characters not on my
keyboard.
So, how do I tell sed to replace a left double curly quote with a
straight double quote, an ellipsis with three periods, or an e with an
acute accent with a normal e among other such things? And if this is
beyond sed's capabilities, could someone suggest another command line
tool that can automate this task?
--
Sincerely,
Jeffery Wright
Bachelor of Computer Science
President Emeritus, Nu Nu Chapter, Phi Theta Kappa.
Former Secretary, Student Government Association, College of the Albemarle.
------------------------------
Date: Sun, 16 Apr 2017 20:58:33 -0400
From: Quentin Young <qlyoung@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Using sed to straighten quotes.
Message-ID: <5ac3210f-acc0-faae-4559-19bd1b4ed5ab@ncsu.[redacted]>
Hi Jeffery,
I think GNU's recode tool is probably your best bet here. I experimented with
Unicode left and right double quotes (U+201D and U+201C) in a UTF-8 encoded
text file and ran the following command:
$ recode UTF-8..ISO-8859-15 file.txt
It converted each of the double quotes down to an ASCII double quote, so it
seems to have some smarts built in. Do note that it overwrites the file given
to it.
On 04/16/2017 08:17 PM, Jeffery Mewtamer wrote:
> I often convert various document formats to plain text because the
> conversion is generally easier than trying to navigate a program that
> can read the document in its original format. Problem is, even when
> the document is in English or another language that uses the Roman
> Alphabet, the converted .txt contains characters my text-mode screen
> reader can't read properly(pronouncing the character as "thorn")
>
> Things like left and right double curly quotes and single right curly
> quotes are the most common offenders, which also screws up my screen
> reader's pronunciation of contractions and possessive, though things
> like ellipsis, em-dashes, and accented letters also cause problems.
>
> Most of these problems can be fixed manually, though it means I often
> spend as much time correcting the file as I do reading it.
>
> I know how to use sed to do global search and replace on plain text
> files, at least where both the string to be found and the string it's
> to be replaced with can be typed, but most of the replacements I'd
> like to make have search strings containing characters not on my
> keyboard.
>
> So, how do I tell sed to replace a left double curly quote with a
> straight double quote, an ellipsis with three periods, or an e with an
> acute accent with a normal e among other such things? And if this is
> beyond sed's capabilities, could someone suggest another command line
> tool that can automate this task?
>
>
Best,
--
Quentin Young
President, LUG @ NC State
------------------------------
Date: Sun, 16 Apr 2017 22:58:13 -0400
From: Jim Turner <jdturne8@ncsu.[redacted]>
To: lug@lists.ncsu.[redacted]
Subject: Re: Using sed to straighten quotes.
Message-ID: <874lxn3flm.fsf@turner.[redacted]>
Hi Jeffery,
Also try the iconv tool. I tested it with an ellipsis, curly quotes, and
an accented 'e', and it turned them into three dots, ASCII quotes, and
an ASCII 'e', respectively. Characters that it can't transliterate are
turned into question marks. You can run it like this:
$ iconv -t ASCII//TRANSLIT original.txt -o output.txt
Jim
On Mon, 17 Apr 2017, at 00:58:33+0000, Quentin Young <qlyoung@ncsu.[redacted]>
wrote:
> Hi Jeffery,
>
> I think GNU's recode tool is probably your best bet here. I
> experimented with
> Unicode left and right double quotes (U+201D and U+201C) in a UTF-8
> encoded
> text file and ran the following command:
>
> $ recode UTF-8..ISO-8859-15 file.txt
>
> It converted each of the double quotes down to an ASCII double quote,
> so it
> seems to have some smarts built in. Do note that it overwrites the
> file given
> to it.
>
> On 04/16/2017 08:17 PM, Jeffery Mewtamer wrote:
>
>> I often convert various document formats to plain text because the
>> conversion is generally easier than trying to navigate a program that
>> can read the document in its original format. Problem is, even when
>> the document is in English or another language that uses the Roman
>> Alphabet, the converted .txt contains characters my text-mode screen
>> reader can't read properly(pronouncing the character as "thorn")
>>
>> Things like left and right double curly quotes and single right curly
>> quotes are the most common offenders, which also screws up my screen
>> reader's pronunciation of contractions and possessive, though things
>> like ellipsis, em-dashes, and accented letters also cause problems.
>>
>> Most of these problems can be fixed manually, though it means I often
>> spend as much time correcting the file as I do reading it.
>>
>> I know how to use sed to do global search and replace on plain text
>> files, at least where both the string to be found and the string it's
>> to be replaced with can be typed, but most of the replacements I'd
>> like to make have search strings containing characters not on my
>> keyboard.
>>
>> So, how do I tell sed to replace a left double curly quote with a
>> straight double quote, an ellipsis with three periods, or an e with
>> an
>> acute accent with a normal e among other such things? And if this is
>> beyond sed's capabilities, could someone suggest another command line
>> tool that can automate this task?
>>
>>
> Best,
------------------------------
End of [lug] Digest (8 messages)
**********